Adding newsfragments for removed executors -- Sequential & Debug#48657
Adding newsfragments for removed executors -- Sequential & Debug#48657amoghrajesh merged 4 commits intoapache:mainfrom
Conversation
Lee-W
left a comment
Lee-W
left a comment
There was a problem hiding this comment.
Is it possible for user to set something to Sequential/Debug Executor in code or config?
|
Nah I do not think so from looking at the code |
|
@Lee-W there is a possibility of doing something of that sort in "core \ executor" config but we shield it now and do not allow it. |
How do people set it to Sequential / Debug in the past? |
|
cc @eladkal maybe you are the right person for this, can these executors be set anywhere in the code / config? |
It was using either the config or env variable: https://airflow.apache.org/docs/apache-airflow/stable/core-concepts/executor/index.html |
Then I think we might still need a config rule then? |
|
Wondering that too. Is it possible to have a rule to override either of those to LocalExec? |
We could add it to the |
|
@Lee-W let me do that yeah |
|
@eladkal that change has been made. I am getting the debugexecutor doc refs removed too. |
Co-authored-by: Wei Lee <weilee.rx@gmail.com>
3 participants
#48579 and #48528 removed Sequential and Debug Executors. We should add significant newsfrags for these as it is a behaviour change for end users.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.